home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19971216-19980424
/
000227_news@newsmaster….columbia.edu _Sat Feb 14 05:51:06 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
5KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id FAA09454
for <kermit.misc@watsun.cc.columbia.edu>; Sat, 14 Feb 1998 05:51:06 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id FAA27710
for kermit.misc@watsun; Sat, 14 Feb 1998 05:51:05 -0500 (EST)
Resent-Date: Sat, 14 Feb 1998 05:51:05 -0500 (EST)
Resent-Message-Id: <199802141051.FAA27710@newsmaster.cc.columbia.edu>
Newsgroups: comp.unix.sco.misc,comp.protocols.kermit.misc
Path: news.columbia.edu!news.new-york.net!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!News.Toronto.iSTAR.net!News.Vancouver.iSTAR.net!news.istar.net!paralynx!paralynx-1!204.174.16.8.MISMATCH!paralynx!paralynx-4!van-bc!xenitec!news
From: Bela Lubkin <belal@sco.com>
Subject: Re: null modem file transfer
Resent-From: mmdf@xenitec.on.ca
Submit-To: scomsc@xenitec.on.ca
Reply-To: scomsc@xenitec.on.ca
Cc: Frank da Cruz <fdc@watsun.cc.columbia.edu>
Organization: work for SCO, speak for myself
Date: Fri, 13 Feb 1998 23:17:38 GMT
Message-ID: <9802131517.aa08163@vagabond.armory.com>
References: <CMM.0.90.4.887299124.fdc@watsun.cc.columbia.edu> <9802130105.aa05971@vagabond.armory.com> <6c2bs9$lo9$1@apakabar.cc.columbia.edu>
Sender: news@xenitec.on.ca (xenitec.on.ca News Administrator)
Precedence: list
Lines: 76
Xref: news.columbia.edu comp.unix.sco.misc:60892 comp.protocols.kermit.misc:8413
Frank da Cruz wrote:
> : > # + for Altos 486, 586, 986 with Xenix 3.0, "make altos"
> :
> : That's the really ancient stuff. I had some live Internet time
> : yesterday and went exploring. I was able to find mention of this Altos
> : Xenix binary in the ".hlp" files; it showed that it would have a prefix
> : of "ck", but gave no guidance on the actual filename. I failed to find
> : the binary. Can you identify it?
>
> Just because the binary was built at one time long ago, that doesn't
> necessarily mean we ever received a copy of it, or even asked for one.
> Back in the old days, all UNIX versions had C compilers, and so it was not
> necessary to build up big collections of UNIX C-Kermit binaries. How times
> have changed, eh?
>
> A hunt through our archives does not turn this one up. I'll add the Kermit
> newsgroup to this thread (the original poster was looking for a way to
> transfer files with Xenix 3.x, which, oddly enough, turns out to be much
> older than SCO Xenix 2.x), in case anybody out there has such an an old Xenix
> handy, with Kermit on it.
>
> : > # + for Tandy 16/6000 with Xenix 3.0, "make trs16"
> :
> : Didn't find this either.
> :
> It's at:
>
> ftp://kermit.columbia.edu/kermit/bin/ckuker.trs16
>
> But this is not an 80x86 so I don't think it would help. For that matter, I
> don't think the Altos was an 80x86 either.
The original poster referred to an "old Xenix 3.0 system" without
mentioning CPU. That's why I'm speculating about the possible CPUs.
Altos 486, 586, 986 (and others in that series) were 8086 machines. I
believe they had special Altos-designed external MMUs so they could
actually run a protected OS (as opposed to SCO's standard 8086 Xenix,
which went through the motions, but could not actually protect processes
from each other -- the hardware didn't support it).
> C-Kermit ran quite nicely on straight UNIX V7 on various hardware platforms,
> but I don't have binaries for that either. Ditto for System III on early PCs
> (PC/IX, etc). We do, however, have a binary for Bell Research UNIX V10 :-).
Huh. A "System III PC/IX" binary might very well work on 8086 Xenix
3.0. But you say you don't have that one either... ;-}
> : > In any case, I also have the very old, old, primitive, tiny version of
> : > C-Kermit from 1982 or so -- it can be used in a pinch on almost any old
> : > version of UNIX.
> :
> : Yes, but now you're a solution looking for a problem. His machine
> : should already have UUCP, and certainly the more recent Unix he's trying
> : to talk to will. So there's no need for Kermit in the first place. A
> : newer version with large packets and sliding windows would improve his
> : transfer rate. An old crufty version will only degrade his transfer
> : rate (94- vs. 128-byte packets, 1- vs. 8-packet window, and unnecessary
> : control char quoting).
> :
> True, but sometimes the crufty old versions are a great way to bootsrap the
> slick new ones. Btw, maximum Kermit packet size is 9000, not 128. Maximum
> window size is 32.
Maximum size supported by the protocol is 9000. What is the likely
maximum size and window supported by the ancient binaries we're trying
to scrounge up? Probably 94 & no windowing. So, again, UUCP will
probably serve better in this case. Kermit's a good program, but it
isn't always the right solution to every communications problem!
>Bela<
--
Back a bit early from our world travels. Vietnam in a few months (we hope).
Travelogue http://www.armory.com/~alexia/trip/trip.html still being updated.